Andrew Durward writes:

Can anybody suggest a different workaround? The problem effectively renders Boost.Test unusable in this configuration when MFC is present.

You can just ignore memory leaks using command line or environment variable