define non-sized deallocator and memory counting debugging

 * it turned out to be possible to provoke memory_usage
   overflows or underruns, resulting in unrecoverable states
 * a possible reason can be that at least with G++ 5.4.0,
   the compiler would sometimes call the (default) non-sized
   delete followed by our custom sized delete/deallocator.
 * This was true even after compiling Scintilla with -fsized-deallocation.
 * therefore we provide an empty non-sized delete now.
 * memory_usage counting can now be debugged by uncommenting
   DEBUG_MAGIC in memory.cpp. This uses a magic value to detect
   instrumented allocations being mixed with non-instrumented
   allocations.
 * simplified the global sized-deallocation functions
   (they are identical to the Object-class allocators).

0 files changed, 0 insertions, 0 deletions