In reply to SV26:
OK, I understand.
With respect what comes first, driver or monitor you do not have any influence because all run_phases are executed in a fork/join. If you want the monitor becoming active after the driver you have to control this with an additional event or another mechanism.
THe driver display you the intruction as it is provided to the DUT. The valid output from the DUT comes 1 clock cycle later.
It is correct what you see.