Question

In order for an application to have no memory leaks, does the number of new in a C++ project match the number of delete?

Answer 1

If you mean do you need the same number of instances of delete in your source code as you have instances of new, then no. You can have objects newed in multiple places, but all these objects deleted by the same line of code. In fact this is a common idiom.

Smart pointers, of varying types, generally take many different objects newed in many places in user code and delete them from a single place in library code.

Edit

Technically, every successfully memory allocation call needs to be matched with a dellocation call that takes the returned pointer from the original allocation call.

Most new expressions result in a call to an operator new that allocates the memory and the constructs an object in the newly allocated memory. Using a delete expression destroys the object and causes a call to an operator delete that should free the allocated memory.

There are new expressions that construct objects in pre-allocated memory (placement new). These should not be matched by a delete expression, but the pre-allocated memory may need to be deallocated in a way that corresponds to the original allocation.