There should be a lot of documents regarding CRPR at Solve-it.
For short, when you run PT with OCV, it creates the worst case scenario, like analyzing setup timing using slow corner for lanunching clock path, and fast corner for capturing clock path. The issue is these clock paths share the common path way upstream of the clock trees and OCV applies the different delay for those clock buffers on the common path. In reality, it is not possible that a single instance has both of slow and fast corner characteristics and CRPR forces those cells common to both of launch and capture clock path to use the same delay.