sql_profile with force_matching=true not adapting to changed literal

We've implemented some sql profiles that include 'force_match=true'. However they're not being used when a literal changes. An example of a literal that we're using is "WHERE CREATE_TIMESTAMP <='07-Dec-2015 11:00:00 PM'". If we change it by one character: '08-Dec-2015 11:00:00 PM', the profile is no longer used. When we observe the changed-literal query running, it shows a different exact_matching_signature and a different force_matching_signature from the original literal query. The profile does not cause the original query to run with bind variables (I'm not at all certain that it should, but I did see some documentation that implied that it would).