They instead took the lead and made a work around for these drivers giving back overclocking ability with the release of Precision 1.9.1.
This work around is ONLY good for the 196.xx series drivers to help insure Nvidia fixes the problem for all in future driver revisions.
Originally Posted by GuRu3D
I've just peeked into issue a bit deeper. The driver uses different domain IDs when reporting and when setting new clocks so it sounds like a bug in the driver and not an intentional overclocking interface evolution. Bugreport is filled and sent to NVIDIA.