FieldManager.UpdateChildren calls in Parent-Child-GrandChild

I see in ProjectTracker...the ProjectEdit calls FieldManager.UpdateChildren(this)

This hits framework code in the listbase which loops through calling Update/Insert/Delete on its children.

If I have another level deeper...

1.  Do I have to also call FieldManager.UpdateChildren(this)? It doesn't seem like this recurses past the first level in the graph right?

2.  Would it be a good habit to call that at the end of each dataportal insert/update just in case some other developer adds a child property and doesn't know CSLA enough to add that...but they would probably copy it if they were just making their own grandchild from my example.  Not much of a performance hit.

Thanks,