GLIBCXX_FORCE_NEW and valgrind

I know a lot has been asked about this, but they are quite old and the situation may be different now. I am running pretty new gcc (4.9.2), libstdc ++ 3.4.21 and valgrind 3.10.1. The problem is that, as you might have guessed, valgrind reports the infamous "still available" blocks, even for a simple program:

int main()
{
  return 0;
}

      

        
        
        
      

    

(that's right, not even one)

Setting GLIBCPP_FORCE_NEW = 1 or GLIBCXX_FORCE_NEW = 1 does not solve the problem. Anyone who managed to find a solution? Is there an alternative to these variables in newer versions of gcc or are people just ignoring it?

Thank!