The issue is Windows, not CVI. CVI timer functions use the Windows timers. I believe Sheetal is right: the highest resolution Windows timers are 1 mS. The default timer in Windows 2000 and XP is 10 mS (earlier versions had 55 mS). The multimedia and performance timer resolutions are 1 mS.
For more info, you can search CVI help for useDefaultTimer or click
here to learn more from Microsoft. Note: you don't have to call SDK code to use the high resolution timers, CVI does that automatically.
Putting a delay in a for loop can give you a delay of less than 1 mS, but, under Windows multi-tasking, that delay will not be predictable. Depending on what else Windows is doing at the time, the execution time of a for loop delay can vary greatly.