I ran this simplistic C-program through valgrind:

int main() {

  return 0;
}

Here is the output:

==35961== Memcheck, a memory error detector
==35961== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==35961== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==35961== Command: ./valgrind.o
==35961== 
==35961== 
==35961== HEAP SUMMARY:
==35961==     in use at exit: 22,100 bytes in 187 blocks
==35961==   total heap usage: 271 allocs, 84 frees, 28,340 bytes allocated
==35961== 
==35961== LEAK SUMMARY:
==35961==    definitely lost: 0 bytes in 0 blocks
==35961==    indirectly lost: 0 bytes in 0 blocks
==35961==      possibly lost: 2,064 bytes in 1 blocks
==35961==    still reachable: 0 bytes in 0 blocks
==35961==         suppressed: 20,036 bytes in 186 blocks
==35961== Rerun with --leak-check=full to see details of leaked memory
==35961== 
==35961== For counts of detected and suppressed errors, rerun with: -v
==35961== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

As you can see there are 2,064 bytes possibly lost and 20,036 bytes suppressed. I've already read about this, but heard that it should be fixed... 
Otherwise is there a way to exclude the system libraries for valgrind?

Reproducible: Always

Steps to Reproduce:
1. Create simplistic program (empty main - no includes). 
2. Run valgrind.

Actual Results:  
2,064 bytes possibly lost.
20,035 bytes suppressed.

Expected Results:  
No lost bytes.