Aha! That's a weird behaviour difference between when constructors ar…

…e called by visual studio vs gcc.

Seems the gcc behaviour is correct. When I init an iterator, CALL THE FUCKING CONSTRUCTOR.
The only reason VS seemed to be behaving correctly (not reallocating the cache) was because
it wasn't calling the constructor. Who knows why?

Caper/MappingEngine.h

@@ -155,8 +155,14 @@ class MappingEngine
 
   iterator End( string & aContigIdent )
   {
+    // HOLY SHIT, THIS METHOD IS ALL WRONG. I'm getting a meaning collision between -1 as End value, and -1 as default starting. 
+    // What an irritating bug.
+
+    cout << "~~MappingEngine - End(contig) - Initing a new one" << endl;
     iterator lIt ( this, aContigIdent ); // does this get destroyed too soon? :/
+    cout << "~~MappingEngine - End(contig) - Ending it" << endl;
     lIt.End();
+    cout << "~~MappingEngine - End(contig) - Done, returning it" << endl;
     return lIt;
   }