Full reactivity doesn't work when pagination is disabled

Nobody has claimed this yet.

First off - thanks for all of your excellent Meteor packages, I use several of them.

Like it says in the title, I have a table where everything works just fine when pagination is enabled.

With pagination disabled, inserts/deletions are not reflected until I reload the page so the table is reloaded. I have some collections where the user can only see their own documents, where they won't have more than 20 at one time - so pagination doesn't really make sense for that use case.

I've tested that the problem exists with multiple different tables, but I guess the issue could be related to one of the other packages I'm using. Call me lazy, but I would love if somebody could verify if they can reproduce this - if not then I will try to come up with a minimal example in a new project without all the extra packages I am using.

My packages file:

```
meteor-platform
less
nemo64:bootstrap
iron:router
zimme:active-route
accounts-password
aldeed:tabular
aldeed:simple-schema
fortawesome:fontawesome
aldeed:autoform
aldeed:collection2
aldeed:template-extension
ian:accounts-ui-bootstrap-3
accounts-google
rajit:bootstrap3-datepicker
aldeed:autoform-bs-datepicker
msavin:mongol
momentjs:moment
matb33:collection-hooks
dburles:collection-helpers
meteorhacks:subs-manager
yogiben:autoform-modals
natestrauser:select2
zimme:select2-bootstrap3-css
juliancwirko:s-alert
juliancwirko:s-alert-genie
```

Start by reproducing the pagination-disabled behavior in a minimal Meteor application, since the issue provides only a package list and no repository files or failing test. Compare inserts and deletions with pagination enabled and disabled, then document a reproducible case and verify that table data updates without a page reload.

Written by the indexing model from the issue text.