Trace.remove_response() without nfft_pow2 option slow for certain npts

Dear developers,

when working with large traces (say, nb of data ~ 1,000,000), the rfft inside 'remove_response' method hangs (on my computer at least).

In 'simulate' method there is an option nfft_pow2, which I always use to get away with this.

Is it possible to add this option to remove_response?

Thanks
BG