Are you sure that even one second passes between two calls?
One option is to convert to float (e.g ((float)clock() - previousTime) / CLOCKS_PER_SEC). However clock() function has quite a high granularity and has a limited applicability. If you are under windows, you may use QueryPerformanceCounter/QueryPerformanceFrequency to make much more accurate measures of elapsed time.
CLOCKS_PER_SEC presumably 1000, and DrawString is going to take less than 1s, so numSecondsPassed will always be < 1. Since it's an integer, it will truncate to 0. Various solutions are available, but we need to know what numSecondsPassed is being used for to give good advice.