The point is that new/delete "know" about your contructor/destructor code. Meaning you get the chance to initalize/cleanup anything you want. Using malloc/free does not give you a chance to do this.

When I have to use strict C I always end up writing functions that do initialization like this:

Example *eg = AllocateExample();

Example* AllocateExample() {
Example *eg = malloc( sizeof(Example) );

eg->variable1 = 0;
eg->variable2 = 0;
eg->variable3 = 0;
.
.
.
}

so that I don''t forget to inialize something. Especially if you have member variables that are pointers...if you forget to initialize them to NULL and the you do a check against NULL somewhere else in your program then you are going to crash when you try to access that pointer.

If you use "new/delete" then you are given 1 place to do all of your initialization.