The following code generates two CA2000 warnings (among others, but that\'s not the point).
public sealed class Item: IDisposable
{
public void Dispose()
Well of course the first thing to do is to actually have the Dispose method clean up the members of the collection. I'm assuming that's just an error in the example rather than the real code.
Beyond that, I would just suppress the warning. I very strongly hold that any suppression:
That said, I think the analysis of CA2000 is so poor as to not be worth having it checked by default, but only in occasional reviews. After a certain number of false-positives a warning can't even be considered a warning any more, just noise that's hiding real warnings and hence making code more likely to be buggy.