FIX: incorrect nested LWF rendering order

Nested LWFs were rendering in incorrect order because Render() was returning an incorrect number of children rendered.

Example: Parent render count 100, Parent render index 3, Child render count 10, should return 0-10, would return 87-97. This would disrupt all render indexes.
Merge pull request #97 from arbieo/master

FIX: incorrect nested LWF rendering order