Article's "Updates" count incorrect in Synchronization History

I have an application that will insert records into a table that is part of Merge replication.  The application does not have any way to update a record.  No-one but the application is accessing the database.  When I look in the Replication Monitor, I see the Inserts which look to have the correct number of Inserted records, but there are hundreds of records that have been recorded as being updated.  This is a bidirectional replicated table but the databases on the Publisher nor the distributer have a means to update records.  I am using a custom resolver for the article.  I am using the Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver.