Feature Request: Improve Coverage Data Collection and Reset Mechanism

[bigWhiteXie]

Hello,

We are currently using Devel::Cover in our project to obtain integrated coverage data. However, we have encountered two significant limitations that we hope can be addressed to improve our workflow:

Coverage Data Collection:

Currently, we collect coverage data by forking the process and then exiting to gather the data. After this, we execute shell commands to generate the coverage report. This process is cumbersome and could be streamlined to enhance efficiency and ease of use.
Resetting Coverage Data:

At present, clearing the coverage data requires a complete restart of the project. This is not ideal, as it disrupts our workflow. We would greatly appreciate a more convenient method to reset the coverage data without needing to restart the entire project.
Proposed Solutions:

For the first issue, it would be beneficial to have a more integrated approach to collecting coverage data that does not rely on forking and exiting processes.
For the second issue, implementing a feature that allows for the coverage data to be cleared or reset programmatically without a full restart would significantly improve usability.
We believe these enhancements would be valuable additions to Devel::Cover and would greatly benefit users who rely on it for coverage analysis in continuous integration environments.

Thank you for considering these suggestions. We look forward to any improvements that can be made in these areas.