suppress based on any callstack in indirect leak group

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on June 08, 2011 06:19:09_

Today only the leak whose callstack is reported will be matched vs
suppression and no indirect leaks will. Since the primary leak reported is
determined by malloc iteration order and can thus be relatively random it
can be difficult to suppress a leak when the primary has a fixed callstack
but there are many, many indirect leaks with very different callstacks.
Apparently this has been a problem: Timur can you fill in details if
possible?

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