Thanks Juris,
I can reproduce the issue. Basically the issue is this:
There appears to be an offset of 65536 for each update added to the correct value. The issue appears to be because of the register that the profile clock reads to obtain the count value. When looking at the value of the pseudo-register CLK in the expressions view, the starting value is always 0x00010000. So this would explain the 65536 offset.
This issue was introduced in CCSv5.5. 5.4 showed the correct value. This is because there is no offset. The starting value of CLK in 5.4 is 0x00000000.
I filed a bug for this. Tracking ID is SDSCM00049339
thanks
ki