Native checksum table says there's a difference, pt-table-checksum does not
Don't worry, your situation is not unique. I encountered the exact same problem with mk-table-checksum years ago (See my Nov 16, 2012 post Maatkit shows the MySQL replication error in one table, but won&#39;t fix it)

Here is something frightening from the MySQL Documentation on CHECKSUM TABLE


  The checksum value depends on the table row format. If the row format
  changes, the checksum also changes. For example, the storage format
  for VARCHAR changed between MySQL 4.1 and 5.0, so if a 4.1 table is
  upgraded to MySQL 5.0, the checksum value may change.
  
  Important If the checksums for two tables are different, then it is
  almost certain that the tables are different in some way. However,
  because the hashing function used by CHECKSUM TABLE is not guaranteed
  to be collision-free, there is a slight chance that two tables which
  are not identical can produce the same checksum.


I meniotned this caveat before back in January 2012 : How to check the consistency of tables in mysql

Sometimes, I just like directly using mk-table-sync (sorry Percona, I'm old fashioned)  with the --print options and tell me the SQL differences. As the MySQL Documentation says, there could be differences because of the VARCHAR alignment or ROW FORMAT. If mk-table-sync/pt-table-sync insists there are no changes, you could trust it 99.9 % of the time. If you don't trust it, mysqldump the table and reload it. Chances are the checksum may not match again.