as one of the sonar-cxx contributors I would like to add a couple of words to the statement of Günter.
There are a variety of commercial SonarQube plugins, which might compete with SonarCFamily: PVS-Studio, Coverity etc. They provide their own static code analysis and they cost money.
On the other hand, there are standard developer tools: cppcheck, clang, valgrind etc. They are not competitors of SonarSource, they belong to the well-established and irreplaceable tool-kit of every C/C++ developer. These tools are free, open-source and (if well integrated) can make SonarQube even more popular among C/C++ developers.
Our plugin allows such integration in a very high-quality way. The issue you’ve quoted is a) not reported at sonar-cxx b) not confirmed to be a sonar-cxx issue c) doesn’t say much about the quality at all. You might take a look at the number of GitHub stars or number of downloads. You’ll see, that sonar-cxx is widely accepted and highly trusted plugin.