limiting code that DProf profiles

[Chris Nokleberg]

I'm using Apache::DProf to profile a mod_perl script. The specific section
I am looking to improve is hard to get meaningful numbers for, because in
the DProf output it is overwhelmed by the time of child process startup
and other things that I'm not interested. Is there a way to limit the code
that DProf profiles? If not, any idea on how difficult it would be to
patch?

Thanks,
Chris