Usually the profiler gives higher execution times than is true, since it is using resources itself. Make sure the profiler is started before starting the program (while in edit mode vs run time mode). Wait for the completion of all vis, then stop the profiler.
Of course, the sub vis may actually execute faster than the profiler can discriminate (eg faster than a microsecond), which happens frequently.
2006 Ultimate LabVIEW G-eek.