Nope Carol, most of the long-term MVP and other members here have been recommending against the use of any registry cleaner including CCleaner since at least the point at which Microsoft shifted their own official stance, pulling the Windows Live OneCare registry cleaner that was once part of the online safety scanner.
This occurred at roughly the time the OneCare antivirus stopped being sold in 2008, though many of us here had been recommending against using registry cleaners for quite a while before that.
The best article I've found that covers this evolution, referencing both the history at Microsoft and the reasons for the change itself, which have to do with changes in the design and operation of the registry since the release of Windows Vista, is the following.
Microsoft does not support use of Registry Cleaners in Windows
So those still holding onto the long past legacy of registry cleaners are actually acting in direct opposition to what Microsoft recommends, no matter what they choose to believe. Typically this is due to the fact that they really have no understanding what a registry cleaner does and doesn't do, especially as relates to the lack of ability to determine whether or not removing something might in truth be damaging to the registry and so the entire operating system.
The problem is that there are no simple standards of what should or shouldn't be removed, since that's typically decided by those designing the original program. So the commonly held belief that any program not currently installed should have everything relating to it removed is actually wrong, since in some cases these legacy keys are required in order to keep that portion of the registry stable.
For this reason it's necessary for the person operating a registry cleaner to fully understand the ramifications of the registry changes they are about to make, which with a moments thought is easy to realize can't be true, since only the original application creator truly knows this for certain. This is the basic flaw that makes all registry cleaning inherently dangerous and precisely why Microsoft itself dropped the Windows Live OneCare registry cleaning module.
A great example is the existence of "First Run" selections within the Office application suite and in fact many programs using the Microsoft Installer, since this type of key is inherently designed to look like an orphaned entry within the registry. The first time I ever tried CCleaner myself many years ago I immediately realized it had mistaken many of these keys within my partially installed Office package, which if I'd allowed it to remove these would have broken their designed ability to prompt for the original installation CD if an attempt was made to open that particular program feature. Instead I immediately uninstalled the actual dangerous program, CCleaner.
If you can't understand what I'm explaining, you're indicating to those here who do precisely why we are so clearly against the use of all registry cleaners. Only those with a deep knowledge of the registry and the individual applications that use it are really capable of making such decisions, but you'll actually find that most of these skilled individuals have stopped using them themselves for this very reason, instead choosing to manually peruse the registry for the specific keys needing to be changed on the rare occasion this might be necessary.
Once the registry cleaning feature is removed from CCleaner, it basically becomes a glorified file cleaner, which since a well behaved system does much of this itself today, is also unnecessary. Whatever the built-in Windows functions don't already do themselves are typically better off done with simple targeted tools designed to remove only well known temporary files for example, rather than a general purpose "cleaner" that tries to perform multiple functions some of which have always required a technically skilled person rather than the typical uninformed consumer PC owner.
Rob