Raise_objection in uvm_sequence class

In reply to peter:

Objections are not phases, they are flags that keep an existing phase active.

The general rule is your test should raise an objection, start the top-level sequence, then drop the objections. If all the blocking child sequences are hierarchical under the top-level sequences, you don’t need another objections.

If you have a sequence in an independent process (via fork/join_none), that sequence may need to raise an objections. What you want to avoid is a situation where you continually raise and drop objections over and over again as that may slow your test down, as well as make it more difficult to debug.