I'm pretty sure valgrind should not report a leak for this.

> cat test.cc 
int main()
{
        return 0;
}

> valgrind --leak-check=full --show-leak-kinds=all ./test 
==11394== Memcheck, a memory error detector
==11394== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11394== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==11394== Command: ./test
==11394== 
==11394== 
==11394== HEAP SUMMARY:
==11394==     in use at exit: 72,704 bytes in 1 blocks
==11394==   total heap usage: 1 allocs, 0 frees, 72,704 bytes allocated
==11394== 
==11394== 72,704 bytes in 1 blocks are still reachable in loss record 1 of 1
==11394==    at 0x4C29110: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11394==    by 0x4EC666F: ??? (in /usr/lib64/libstdc++.so.6.0.21)
==11394==    by 0x400E8E9: call_init.part.0 (in /lib64/ld-2.19.so)
==11394==    by 0x400E9D2: _dl_init (in /lib64/ld-2.19.so)
==11394==    by 0x40011C9: ??? (in /lib64/ld-2.19.so)
==11394== 
==11394== LEAK SUMMARY:
==11394==    definitely lost: 0 bytes in 0 blocks
==11394==    indirectly lost: 0 bytes in 0 blocks
==11394==      possibly lost: 0 bytes in 0 blocks
==11394==    still reachable: 72,704 bytes in 1 blocks
==11394==         suppressed: 0 bytes in 0 blocks
==11394== 
==11394== For counts of detected and suppressed errors, rerun with: -v
==11394== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)