You can use _CrtDbgBreak in the watch window, to break at the block allocation that generated the leak. But you need to get a reproduceable scenario, with the same allocation numbers generating leaks for each run.