Fix for using ngResource

ngResource adds two fields to collections that are returned: $promise and $resolved.

This PR skips any markers with that name. I had to add this locally and figured others may run into the same issue if they are loading markers from an external service.

Technically, if someone actually named their marker either of those names it would skip, but that seems unlikely!