My experience with it is now rather dated, but BoundsChecker was(is?) more of a developer support tool than it is an anyone-can-use-it test tool. You can't just fire it up, point it at an application and then pass a 'leak list' off to someone to address.
It exposes a surprising number of core-language leaks within the development tools' output so you must have the language expertice necessary to sort out unaddressible tool issues from the ones that came from your own coding effort.
From a testers' perspective, you'll need engineering cooperation for memory maps and implementation and language expertice. In this mode of operation, it's usually expedient to detect a problem using other means, then use BoundsChecker to nail down the source if it isn't readily identifiable.
This is not exactly what you are looking for, but i thought you should take a look.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Iím hoping this article will help a few of you who are currently struggling with Bounds Checker and other memory leak detection tools. In my experience, this simple little class has proved many times more useful in detecting memory leaks than any tool and much cheaper -- Randy Charles Morin<HR></BLOCKQUOTE>