I can reproduce this with compiler version 0.4.12+commit.194ff033.Emscripten.clang (but, in my case, the other way round - file1.sol has a deployment cost of 68990, file2.sol has a deployment cost of 68926.)
There is a 64 gas difference in the cost between the two deployments. The reason for this is that, although the deployment code is exactly the same length (82 bytes), one of the sets of bytecodes has a zero byte in a place where the other has a non-zero byte.
When transmitting a transaction to the blockchain, the gas cost per byte of calldata is 68 for non-zero bytes, and 4 for zero bytes (Appendix G of the Yellow paper, G_txdatanonzero vs. G_txdatazero). Hence the 68 - 4 = 64 gas difference between your codes.
The different byte actually occurs in the appended contract metadata section, not in the deployment code or the deployed code itself which are identical for both your examples as you would expect. The following are the metadata sections for the contracts - the metadata is generated automatically by the compiler and comprises a Swarm hash of the contents of the source file plus some other bits and pieces:
zero/non-zero byte difference is here ^^
So, with two near identical source files you have some chance of there being a difference in deployment cost due to this, and it is compiler version dependent since the compiler version is embedded in the data used to create the Swarm hash.