You can always set up a timer and a counter to do this. Set up a counter with a preset of 100 cycles and increment it once each scan. Record the timer's current value to two different registers, once when C=0 and once when C=100. Subtract the difference, divide by 100, and that will be your scan time (in whatever units your timer is counting in - hundredths, thousandths, etc). The scan time may be slightly larger due to these extra few calculations, but in a medium to large sized program the percentage error will be negligable. You can always subtract out the 'textbook' execution times for the cycles that you added to correct for this.
I have not worked with this processor, so there may be a built in function to show min/max/avg scan time. Someone else will definitely chime in if this is the case.