Finding bottlenecks in MSP code

It’s easy enough to pull out a section of a regular max patch, and run it 100k times in succession as a benchmark. But I’m not sure how to do this kind of thing with MSP patches. Is there a more useful way to judge the system usage of bits of MSP patches than just looking at the CPU meter?