In reply to Srini @ CVCblr.com:
I don't think there's anything bad about that coding style.
Normally when you replace a virtual method you completely replace the parent class code. Copy/pasting is never a good coding practice. If you need only a small tweak, the best solution is to modify the parent class to isolate that specific behavior to its own method which you can then replace. Unfortunately that's not feasible since this is part of the UVM BCL.
What behavior are you trying to modify? Perhaps we can find a better way than copy/paste/tweak.