title: New vs. Malloc, when overloading New
body: <p>I'm overloading <code>new</code> and <code>delete</code> to implement my own small-objects/thread-safe allocator.</p>
  
  <p>The problem is that when I am overloading <code>new</code>, I cannot use <code>new</code> without breaking universal causality or at least the compiler.  Most examples I found where <code>new</code> is overloaded, use <code>Malloc()</code> to do the actual allocation.  But from what I understood of C++, there is no use-case for <code>Malloc()</code> at all.</p>
  
  <p>Multiple answers similar to this one, some with less tort outside of SO:  <a href="https://stackoverflow.com/questions/184537/in-what-cases-do-i-use-malloc-vs-new">In what cases do I use malloc vs new?</a></p>
  
  <p>My question, is how do I allocate the actual memory when overloading operator <code>new</code> without using <code>Malloc()</code> ?</p>
  
  <p>(This is out of curiosity more than anything, try not to take the reasoning behind the overload too seriously; I have a seperate question out on that anywho!)</p>