Static analysis of variable usage from Rider in CLion?

In Rider there are hints about usage of mostly everything but not in CLion; if I stop using a variable after a refactor, for example, said variable will be grayed out and Rider will hint me about it having zero usages, this also applied to methods and properties, but the same isn't present in CLion apparently. I have to manually check each and every variable and function to know if they're being used or not. I assume this has to do with the complexity of C++ but is this really not doable in CLion? Have the tips about how many usages a variable or function have.