Yeah, same thing here. I opened a case on it and I was directed to submit an enhancement to get it fixed/changed. CCC is looking at the "host memory" metrics for the VM from vCenter instead of what percentage the VM is actually using on the host (from VMWare's perspective). The host memory metric almost always shows 100%. CCR is showing the VM's utilization fine and the typical up/down patterns (again, the VMWare perspective though).
But, neither of these are particularly useful in many cases. We need the guest's perspective of memory util in each tool and that isn't happening when pulling from just vCenter. Need to be able to merge data from another source, from the guest, for this to be useful for all server owners/application teams. I love having to explain this new fancy tool is wrong and they have to use something else to see their VM's memory usage properly. Still, the host/cluster memory util is useful for those of us managing capacity of the clusters. Our biggest desire for this info is coming from those that use the VMs and want to know what those really look like. At least we have the CPU utilization correct.