[sldev] VWR-2765 Mozilla libraries interfer with memory types tracking (Client => Consoles => Memory)

[Soft]

I don't have the bandwidth to look into this, but it came up in
today's open source meeting and looked important, so I thought I'd try
bouncing one off the list:

http://jira.secondlife.com/browse/VWR-2765

VWR-2765 Mozilla libraries interfer with memory types tracking (Client
=> Consoles => Memory)

>From the description, I'm guessing we're overloading new and delete in
the preprocessor if some #defines are set, and then we're including
some headers that are also included when building llmozlib2. The
result would be that we have some objects being created with one
new/delete scheme, and freed with another.

Anyone want to verify that this is what's happened? If so, is it as
simple as moving some functions using new/delete out of headers, or is
the solution more disgusting?