Different statistics in _TableStat vs. _UserTableStat

Differences between _TableStat statistics and _UserTableStat statistics
Number of reads reported by _UserTableStat lower than values in _TableStat
Number of writes reported by _UserTableStat lower than values in _TableStat
Number of deletes reported by _UserTableStat lower than values in _TableStat
Number of gets reported by _UserTableStat lower than values in _TableStat
Why are there differences between the number of reads, writes, deletes or gets reported by the  _TableStat VST vs. the _UserTableStat VST?

_TableStat VST

• Reports access statistics for a given table or range of tables (-tablerangesize) since the database was started. 
• Use _TableStat to read persistent statistics that have accumulated since the database was started and can be cleared by running PROUTIL -C zerostats, further outlined in Article: Can PROMON and VST counters be reset to zero while the database is online?
• For example, the number of times read access has occurred does not necessarily equate to the number of records that have been read but rather to the number of times the table has been accessed by the storage engine. This is not the number of record fragments read but the number of individual records read from the database (buffer pool).
• A code example to monitor _tablestat for a sample interval is provided in Article Simple program to monitor record I/O stats for a database  

 _UserTableStat VST

• Reports access statistics about a given table or range of tables by connected user ( -tablerangesize * (-n + -Mn +1)) 
• As soon as users sessions are disconnected from the database, their _UserTableStat statistics are cleared from memory as these are specific only to that connected user's session for the time of their activity.
• A code example to report  on data from _UserTableStat using a temp-table with indexes is provided in Article:  Improving performance when querying the _UserTableStat VST