Computation Bound not explicit in existing documentation

[samueldgSBCS]

The double moving windows implementation is unfit to most production implementation due to the fact that the latest data point is unexplored by the window most of the time (at the time of indicator computation).

func_arg_map = [( obs_copy[:, i:window_size + i], window_size, i, smallest_window_size, outer_increment, inner_increment, max_searches, ) for i in range(0, obs_opy_len+1, outer_increment)]
I suggest adding the option to start the iteration at (obs_opy_len % outer_increment) to make it usable in monitoring or backtest applications without branching the project.

[Joshwani]

Thanks @samueldgSBCS would you be willing to post a draft PR with your suggestion?