title: OpenCV , CRT: Improve Memory Leak detection
body: <p>I'm using openCV 2.4.10 and Visual Studio 2013. After closing my App in Debug-Mode. I get a lot of stuff like this</p>
  
  <p>{237} normal block at 0x00000000004CF790, 48 bytes long.</p>
  
  <p>Data:  47 65 6E 65 72 61 6C 69 7A 65 64 48 6F 75 67 68</p>
  
  <p>{236} normal block at 0x00000000004CF710, 16 bytes long.</p>
  
  <p>Data: &lt;  L             > E0 FA 4C 00 00 00 00 00 00 00 00 00 00 00 00 00 </p>
  
  <p>{235} normal block at 0x00000000004CF690, 16 bytes long.</p>
  
  <p>Data:  47 65 6E 65 72 61 6C 69 7A 65 64 48 6F 75 67 68 </p>
  
  <p>{223} normal block at 0x00000000004CFA20, 48 bytes long.</p>
  
  <p>Data:  47 65 6E 65 72 61 6C 69 7A 65 64 48 6F 75 67 68 </p>
  
  <p>...</p>
  
  <p>The "leaks" aren't growing so it seems to me, it is caused by static allocation in the OpenCV libs i'm using.</p>
  
  <p>My Problem is, that i can easily miss real memory leaks in this mess of false positive. Therefore i want to improve the output. </p>
  
  <p>I can think of two solutions:</p>
  
  <p>1.) Exclude magically the libs from the CRT-Report</p>
  
  <p>2.) Get for every memory leak filename and line</p>
  
  <p>for 2) I tried the following</p>
  
  <ul>
  <li>using visual leak detector didn't improve</li>
  <li>added _CRTDBG_MAP_ALLOC</li>
  </ul>
  
  <p>both didn't work. Have someone a suggestion.</p>