In reply to Shyamsunder:
It’s hard to giver you an answer without more specific details about how your design works.
Generally, it’s a good idea to keep delay information away from your testbench/checkers, especially when the delay is an implementation artifact, and not a requirement. Once your testbench is at a transaction level of abstraction, clock cycle should no longer matter.