A Visual Studio 2022 Solution, named Tests, references a number of projects under a Shared directory:

+---Shared
¦   +---Dates
¦   +---Deltas
¦   +---Instruments
¦   +---Toolis
+---Tests
    +---cpputest
    ¦   +---cmake
    ¦   +---include
    ¦   ¦   +---CppUTest
    ¦   ¦   +---CppUTestExt
    ¦   +---lib
    ¦   ¦   +---x64
    ¦   +---m4
    ¦   +---src
    ¦   +---tests
    +---packages
    ¦   +---msado15.6.1.7601.17857
    ¦   +---msxml6.6.30.7601.18431

Everything compiles and a smoke test inside of Tests runs and a memory leak is caught. The test.cpp file includes the following header file, named LeakDetector.h:

#pragma once

#ifdef DEBUG_NEW
# undef DEBUG_NEW
#endif
#ifdef new
# undef new
#endif

#ifndef CPPUTEST_USE_MEM_LEAK_DETECTION
# define CPPUTEST_USE_MEM_LEAK_DETECTION 1
#endif

#include "CppUTest/MemoryLeakDetectorNewMacros.h"
#include "CppUTest/MemoryLeakDetectorMallocMacros.h"

#ifdef new
# undef new
#endif

#define new new(__FILE__, (size_t)__LINE__)

However, a known and verified memory leak within the Shared/Deltas project isn't being detected, likely because the definition of new isn't being applied to the separate compilation units.

Does anyone have any experience enabling leak detection in CppUTest across different compilation units? Is there a tutorial or example setup showing how to configure a Solution to check for memory leaks across all included projects (without modifying the projects)?

I've tried using properties sheets to inherit includes, but haven't managed to make it work.