I *think* it can, but I'm not certain.  I think it can do checkpoints, and
you have to take checkpoints at different times and diff them.  I *think*.

You can try our tool CodeSnitch (not free though).  It does work on drivers,
but you have to use the info it gives you and analyze on your own.  The
problem is that these tools really don't determine what has leaked until a
program terminates.  Typically the device driver host process never
terminates (they usually run in the context of the system process device.exe
which never terminates).

With CodeSnitch, you get an event for each alloc/free in a listview (UI runs
on desktop).  Each event is color-coded.  When a block gets allocated, you
see it show up in blue.  When freed, the alloc event turns gray (the free
event is gray, too).  So what you can do is look at each blue alloc
(hopefully there aren't a lot in your driver unless there really is a leak)
and then make an assessment based on your code and how your driver works if
it looks like a leak that needs to be corrected.

Follow link below for more info.  There is a free (limited) eval.  If you
try it, in addition to the eval download, you need to install another piece
for it to work with device drivers.  From the main page, go to Utilites and
search for "csdelay.exe".  Instructions included.