Do you use some methology like the ''resource managent'' that www.relisoft.com teaches or are you just trying delete allocated memory otherwise. I''d like to here what others do because I''ve reading those articles for a while and I''m not really sure about it.

I assume you''re referring to this article:
http://www.relisoft.com/book/tech/5resource.html

(Interesting site, by the way; I hadn''t been there before. I have to say, though, that I take exception to their hostile attitude toward MFC, at least from some of the front-page articles I read)

In a word, Yes. Those are some very good guidelines. If you encapsulate resources with ctors and dtors that do acquisition & release, and you try to keep things on the stack if possible, or make sure that the encapsulating object''s destructor explicitly calls delete, you have a very robust system. We seriously started cracking down on this at my work, and we''ve found our software become a lot more reliable in recent revisions.

The "methology" is known as smart pointer wrappers.

The std::auto_ptr is one of such example.