Warnings and metrics for an anonymous method that is declared in a member, such as a method or accessor, are associated with the member that declares the method. They are not associated with the member that calls the method.
Warnings and metrics for an anonymous method declared as an inline assignment to a field are associated with the constructor. If the field is declared as static (Shared in Visual Basic), then the warnings and metrics are associated with the class constructor; otherwise, they are associated with the instance constructor.
For example, in the following class, any warnings found in the declaration of anonymousMethod1, will be raised against the implicitly generated default constructor of Class. Whereas, those found within anonymousMethod2, will be applied against the implicitly generated class constructor.
A class could contain an inline anonymous method that assigns a value to a field that has multiple constructors. In this case, warnings and metrics are associated with all the constructors unless that constructor chains to another constructor in the same class.
Delegate anonymousMethod = delegate()
Even though this might seem unexpected, this occurs because the compiler outputs a unique method for every constructor that does not chain to another constructor. Because of this behavior, any violation that occurs within anonymousMethod, must be suppressed separately. This also means that if a new constructor is introduced, warnings that were previously suppressed against Class(int) and Class(string) must also be suppressed against the new constructor.
You can work around this issue in one of two ways. You could declare anonymousMethod in a common constructor that all constructors chain. Or you could declare it in an initialization method that is called by all constructors.