Suppressions should support field which limits the number of reports it can suppress

_From [rnk@google.com](https://code.google.com/u/rnk@google.com/) on December 14, 2011 15:35:54_

We could use count= or limit= for the field name.

This is especially useful for memory leaks, which if they happen once in the process lifetime, are not a big deal, but if they happen repeatedly, can accumulate and become a problem. If we add the count= field, it would allow the user to suppress such one time leaks, but be alerted if the suppression starts to fire repeatedly.

We could also try to implement some kind of variable substitution or mechanism to say, "this should leak every time I do foo" where foo could be load a library, call a certain function, or fork the process. IMO just having a constant limit would be helpful for most users, though.

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=720_