The only reason is that ID fields are represented as "long" in Java. The SQL Server driver translates these to BIGINT, so it's really a driver doing, not Aware IM's.
The reporting tool could be smarter and not cause a data mismatch for such compatible types.