Generate Change Script - current_date and current_timestamp being flagged

We use current_date and current_timestamp in the PostgreSQL model, which the database engine translates to ('now':text)::date and now(), respectively. These get flagged by the Generate Change Script wizard. Can a future enhancement either recognize these or allow them to be recognized as matching?